Release 10.1A: OpenEdge Development:
Java Open Clients

Mapping temp-table field data types and meta data

The mappings for the individual fields of a temp-table differs from the mappings available for other types of proxy method parameters. Also, OpenEdge supports a common mechanism for specifying the 4GL data types of temp-table fields in the meta data for Java parameters that map to them.

Java data type mappings for temp-table fields

The Java data types for mapping a temp-table fields differ between the OpenEdge ProDataGraph and SQL ResultSet interfaces, because of the differences between the Java SDO and JDBC standards. For the list of Java data types available to map temp-table fields using a ProDataGraph, see Chapter 5, " Accessing Progress ProDataSets." For the list of Java data types available to map temp-table fields using an SQL ResultSet, see Appendix C "Passing Temp-tables as SQL ResultSet Parameters."

Meta data for specifying the 4GL data types of temp-table fields

The Java Open Client does support a common mechanism for specifying the 4GL data types in the meta data for temp-table fields, whether they are mapped using the OpenEdge ProDataGraph or the SQL ResultSet. This meta data support is provided by the com.progress.open4gl.Parameter class. Wherever you specify the 4GL data type of an individual temp-table field, you can use the Parameter class constants listed in Table 4–5. Thus, the sections of this manual that describe how to create temp-table field meta data refer to the class contants listed here.

Table 4–5: Parameter class constants for temp-table field meta data 

Progress temp-table field data type	com.progress.open4gl.Parameter class constant
BLOB	PRO_BLOB
CHARACTER	PRO_CHARACTER
CLOB	PRO_CLOB
COM-HANDLE	PRO_COMHANDLE
DATE	PRO_DATE
DATETIME	PRO_DATETIME
DATETIME-TZ	PRO_DATETIMETZ
DECIMAL	PRO_DECIMAL
INTEGER	PRO_INTEGER
LOGICAL	PRO_LOGICAL
RAW	PRO_RAW
RECID	PRO_RECID
ROWID	PRO_ROWID
WIDGET-HANDLE	PRO_WIDGETHANDLE